pp108 : Deploying Applications using Application Deployer

Deploying Applications using Application Deployer
This topic describes the procedure to deploy applications using Application Deployer.

Before you begin this task
Application deployment has strict prerequisites to ensure a smooth deployment. Ensure that you adhere to the following requirements before beginning to deploy an application:

  • You must have the role of systemAdmin to deploy or upgrade an application.
  • The System Organization must be your default organization to deploy or upgrade an application.
  • Before upgrading an application, it is recommended to take a backup of the LDAP content, database, and the filesystem related to the application, manually.
  • To deploy an application with the system environment variables, DLL registration, or virtual folder creation as content on a windows based machine, you must change the access rights. Refer to Installing an Application With System Environment Variables Content for more information.
  • If the application to be deployed has a dependency on other applications, ensure that these applications are deployed or available for the deployment.
  • The version of the application you are deploying is the same as the version of the runtime reference. A version mismatch can potentially result in the deployment failure.
  • To deploy an application that is signed by a valid certificate.
  • The required Service Containers are started and running. Deployment of artifacts requires the related Service Containers to be available.
  1. On CUSP > My Applications, click (Application Deployer). The Deployment Overview page appears, displaying all the applications in the Applications List pane on the right-side.
  2. Click Browse in the Deployment Overview page, if your application does not appear in the list; select the required application, click OK and do one of the following:
    • Click Upload to upload the application and deploy it at a later point of time. The selected application is displayed in the Applications List pane.
    • Click Upload and Deploy to upload and start the deployment process. The Application Deployer wizard is displayed. If you use this option, you can skip the third step described in this topic.

      Note: Alternatively, you can copy the application packages to be installed to the <Process Platform Installation Directory>/capcontent/packages folder.
  3. Right-click the required application and select Deploy. The Application Deployer wizard appears displaying the Selected Applications screen.
    Note: Alternatively, you can select Express Deploy if you are sure of the dependencies and the signature of the packages. You will be taken to the Application Summary screen directly.
  4. Click , select the version of the package to deploy, and click OK. By default, the latest version is selected.
  5. Click Next to continue. The Package Impact wizard appears, displaying the list of actions that will be performed on the selected packages and their dependencies.
  6. Click Next to continue. The Application Signature Verification Status page is displayed.

    This page is displayed only if one or more applications fail the signature verification. If the status of an application appears to be tampered with or unsigned, and you still want to proceed with the deployment, select the option for that application. Ensure that the security permissions to deploy are set to Prompt or Allow. To allow all the packages for deployment, you can choose 'Select All' option.
    Additionally, if you are deploying in a distributed setup and signature verification fails, then you must ensure one of the following:

    Note: If you are not allowed to deploy the application, contact the system administrator and retrieve a relevant signed application.
    The signature verification of the applications is done.

  7. Click Next to continue. The Impact Analysis window is displayed. It will display the artifact information of the first package. To view the artifact impact of other packages, choose the package from the list. 
    Note: In case of a cluster setup, which has primary and secondary nodes, the impact gives an overview of which artifact is deployed on the primary node and which one is deployed on the secondary nodes
  8. If you have selected to deploy an MDM model, you must do the following in the User Inputs  page:
    1. Select the proxy user and the MDM proxy user from the drop-down list that are required to communicate with other applications on Process Platform
      1. You may select an existing MDM Publisher service group or configure a new one:
        1. Click to select an existing MDM Publisher service group.
        2. Click to configure a service group. The Hub Publisher field is selected by default. Refer to Fields for Configuring MDM Service Groups for information on the fields. 
          Note: The MDM Publisher and the MDM Service service groups that are associated with the MDM model must not be renamed after the model is deployed successfully.
      2. Click Next to continue.
        Note: If you are deploying an MDM model in a primary-distributed setup, it is adequate to deploy it in the primary computer alone. 
        Select the primary node alone in the screen displayed and click Next.
  9. Click   Next to continue. The Applications Summary page appears, displaying the actions that will be performed on the available nodes of the package.
  10. You can do the following in the Applications Summary page.
    1. Select the Revert on failure option to revert the deployment action in case of failure. Note: If the application fails to install, the status of the application is displayed as incomplete on the Deployment Overview page. Refer to Redeploy or undeploy the incompletely loaded application to complete the installation.
    2. Specify the timeout value for the deployment in Timeout (in minutes) . This specifies the time to be taken for the application deployment. The client gets timed out after this period.
    3. Select the Save as Template option and provide a name in the Template Name to reuse the deployment scenario later. The list of created templates will appear on the Deployment Overview page. You can right-click a template and deploy it or view and delete the template. Refer to Using Custom Templates for information on using these templates. The list will be empty if there are no templates created.
  11. Click Deploy to complete the process.
    The application is deployed using the Application Deployer task.

Note:
If you are deploying Cordys BAM MDM Model application package, do the following:

  1. If Process Platform is migrated from earlier versions to Cordys BOP 4.1 CU7.1 and eventually to the later versions, you must execute the database scripts available at the following location: <Process_Platform_Installation_Directory>\components\bam\database\application\dropscripts\BAM_SYNC_TABLES_<<Database_Vendor>>.sql
    This script must be executed against the database configured for the BPM service container. You need not perform this task if you have directly installed Cordys BOP 4.1 CU7.1 and eventually migrated to Cordys BOP 4.2.
  2. Refer to the Loading Cordys BAM MDM Model application package section of the Post-installation Steps in the Process Platform Installation Guide.